Taught by working ops engineers since 2015

Grow from sysadmin to senior — one real skill at a time

We help system administrators level up on the work they already touch: incidents, automation, access reviews, the messy on-call stuff. No fluff. Cohorts are small — usually 11 to 14 people.

Advisor calls run about 20 minutes. No sales script — honest.

What a cohort looks like

  • Nine weeks, one evening session a week, plus lab time you schedule yourself.
  • Real scenarios from real environments — sanitized, but not made up.
  • A mentor who's carried a pager. You can ask the dumb questions.

11–14

learners per cohort

92%

finish the full track

2015

year we ran our first cohort

840+

admins through our programs

4.7/5

avg. post-track rating

~20 min

typical advisor call

The learning tracks

Pick the stage you're stuck at

Most people don't need a whole new degree. They need the next rung. Each track maps to a stage of the operations lifecycle — assess, build, run, and stretch into leadership.

Assess & Plan

You're drowning in reactive tickets and want a map. This track teaches you to audit what you run, flag the risky bits, and write a plan your manager will actually read. Ends with a documented access and inventory review of your own environment.

Build & Automate

Stop doing the same fix forty times a month.

  • · Scripting patterns that survive the person who wrote them
  • · Config management without turning your weekend into a rollback
  • · Writing runbooks a tired colleague can follow at 3am

Run & Respond

The on-call track. We walk through incident command, clean escalation, and the blameless retro — using tabletop exercises based on outages that really happened (names scrubbed). By the end you'll run an incident call without the panic.

Lead & Mentor

For the senior admin being nudged toward a team-lead role. Delegation, reviews, hiring, and saying no to scope creep. It's less about tools here — more about the human side nobody trained you for.

One honest caveat: we don't offer vendor-specific exam prep. If your goal is a single product certificate and nothing else, we're probably not the right fit — and we'll tell you that on the call.

From first call to finished

How a track actually goes

01

We talk first

A short call to figure out where you are and what you're reaching for. If a track fits, great. If not, we point you somewhere better.

02

You join a cohort

Weekly live session, hands-on labs between them, and a small group working through the same material. You'll know your cohort-mates by week two.

03

You ship something real

Every track ends with a deliverable tied to your own job — a runbook, an audit, an automation. Something you can point to in a review.

Results in their words

What graduates told us after

Honestly? I signed up half-expecting another slide deck. The incident tabletop in week four changed how our whole team runs on-call now.
Marcus Boyd
Infrastructure Admin, Granite Peak Logistics
I came in to fix our documentation mess. Built an automation deliverable for the Build track and it cut our monthly patch window from a full Saturday down to about two hours. My manager noticed. That's rare.
Priya Nadkarni
Systems Engineer, Cedar Hollow Health Network
The Lead track was uncomfortable in a good way. I'd been promoted to team lead with zero prep and was quietly flailing. The sessions on delegation and running reviews gave me a vocabulary I didn't have. Took the full nine weeks. Worth every one.
Dana Whitlock
IT Operations Lead, Front Range Credit Union

Next cohort starts in a few weeks

Seats fill because the groups stay small on purpose. Grab 20 minutes with an advisor and we'll tell you honestly whether it's a fit.

Talk to an advisor

Before you ask us

Common questions

Do I need a certain job title to join? +

No. If you're responsible for keeping systems running — whatever your title says — you'll fit. We've had help-desk folks moving up and twelve-year veterans sitting side by side.

How much time per week, really? +

Plan on one live evening session plus roughly three to four hours of lab work you schedule yourself. Some weeks run lighter. The incident week runs heavier — we won't pretend otherwise.

Is it online or in person? +

Both. Live sessions are remote so you can join from anywhere. A couple of times a year we host an in-person lab day at our Denver space for people in the region who want it.

How does pricing work? +

Pricing depends on the track and whether your employer is sponsoring you. We quote it plainly on the advisor call — no tiered upsell maze. Many learners expense it through a professional development budget; we provide an itemized receipt for that.

What if I fall behind? +

Life happens. Sessions are recorded, and if you miss too many we'll roll you into the next cohort at no extra cost — once. We'd rather you actually learn it than rush to a finish line.

Who teaches the sessions? +

Practitioners. Everyone leading a track has spent years doing the work — carrying on-call, running migrations, cleaning up after the bad deploy. Not career instructors reading from a manual.

Not ready to talk yet?

Get our curriculum guide — the full week-by-week breakdown of every track, what you'll build, and the time it takes. It lands in your inbox. No call required.

Book a planning call

Let's figure out your next step

Twenty minutes, no pitch. Tell us where you're at and we'll map a track to it — or send you elsewhere if that's the honest answer.

Office hours: Mon–Fri, 8:00–17:00 MT

How would you like to meet?